增加 tnf config 命令

➜  tailwindcss git:(feat-config-command) npx tnf config list

  Configs:

 - [key: router] { defaultPreload: 'intent' }

 - [key: tailwindcss] true


➜  tailwindcss git:(feat-config-command) npx tnf config get tailwindcss

  Configs:

 - [key: tailwindcss] true


➜  tailwindcss git:(feat-config-command) npx tnf config set tailwindcss false

set config:tailwindcss on .tnfrc

➜  tailwindcss git:(feat-config-command) ✗ npx tnf config get tailwindcss

  Configs:

 - [key: tailwindcss] false

➜  tailwindcss git:(feat-config-command) ✗ npx tnf config remove tailwindcss
remove config:tailwindcss on .tnfrc

➜  tailwindcss git:(feat-config-command) ✗ npx tnf config get tailwindcss   

  Configs:

key 'tailwindcss' not found

其他命令可以 import { setConfig } from 'src/config/config.ts' 来修改配置文件

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC. Roadmap #2
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests

• Run the tests and other checks with pnpm ci

Changesets

• If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features and fix bugs should all be patch before we release 0.1.0. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

• Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.